Dynomotion

Group: DynoMotion Message: 3719 From: himykabibble Date: 2/4/2012
Subject: VS2008 Question
Brad,

Thanks to Tom, I got my app moved over to VS2008, so I can now debug down into the DLLs (it appears VS2010 Express does not support this). It's all working fine on my laptop, but I also need it working on the PC on my machine. I copied over my entire KMotion428 tree, along with the project tree for my app. However, when I try to open BuildAllLibs.sln, I get an error message on KMotion_dotNet.csproj that reads:

Unable to read the project file KMotion_dotNet.csproj
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9): The attribute "Returns" in element <Target> is unrecognized.

I have had no success trying to understand what the problem is, much less resolve it. I suspect it has something to do with the fact that VS2008 does not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't know how to fix this. It clearly CAN be fixed, since it is working on my laptop.

Regards,
Ray L.
Group: DynoMotion Message: 3726 From: himykabibble Date: 2/5/2012
Subject: Re: VS2008 Question
OK, I've just learned something about the vagaries of .NET and VS2008. VS2008 does not fully understand .NET 4.0, and will sometimes get confused if you're running a project that uses it. This happened on the PC on my machine yesterday, and it happened on my laptop today. I spent hours trying to figure out what was wrong and how to fix it, with no joy. Then I stumbled across a simple fix - Under Project->Properties->Application, I set the target Framework to .NET 1.0, knowing full well it would break everything. And boy did it! I then set it BACK to .NET 3.5, and now life is good, and everything works as it should!

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> Thanks to Tom, I got my app moved over to VS2008, so I can now debug down into the DLLs (it appears VS2010 Express does not support this). It's all working fine on my laptop, but I also need it working on the PC on my machine. I copied over my entire KMotion428 tree, along with the project tree for my app. However, when I try to open BuildAllLibs.sln, I get an error message on KMotion_dotNet.csproj that reads:
>
> Unable to read the project file KMotion_dotNet.csproj
> C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9): The attribute "Returns" in element <Target> is unrecognized.
>
> I have had no success trying to understand what the problem is, much less resolve it. I suspect it has something to do with the fact that VS2008 does not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't know how to fix this. It clearly CAN be fixed, since it is working on my laptop.
>
> Regards,
> Ray L.
>
Group: DynoMotion Message: 3727 From: Brad Murry Date: 2/5/2012
Subject: Re: VS2008 Question

Everything works until the new .NET library is available in 4.29……  mu hu ha ha hah!

 

 

There are lots of tightened bolts and extra goodies, so I do believe it will be work the effort to update.

 

-Brad Murry

 

From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
Sent: Sunday, February 05, 2012 6:29 PM
To: DynoMotion@yahoogroups.com
Subject: [DynoMotion] Re: VS2008 Question

 

 

OK, I've just learned something about the vagaries of .NET and VS2008. VS2008 does not fully understand .NET 4.0, and will sometimes get confused if you're running a project that uses it. This happened on the PC on my machine yesterday, and it happened on my laptop today. I spent hours trying to figure out what was wrong and how to fix it, with no joy. Then I stumbled across a simple fix - Under Project->Properties->Application, I set the target Framework to .NET 1.0, knowing full well it would break everything. And boy did it! I then set it BACK to .NET 3.5, and now life is good, and everything works as it should!

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> Thanks to Tom, I got my app moved over to VS2008, so I can now debug down into the DLLs (it appears VS2010 Express does not support this). It's all working fine on my laptop, but I also need it working on the PC on my machine. I copied over my entire KMotion428 tree, along with the project tree for my app. However, when I try to open BuildAllLibs.sln, I get an error message on KMotion_dotNet.csproj that reads:
>
> Unable to read the project file KMotion_dotNet.csproj
> C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9): The attribute "Returns" in element <Target> is unrecognized.
>
> I have had no success trying to understand what the problem is, much less resolve it. I suspect it has something to do with the fact that VS2008 does not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't know how to fix this. It clearly CAN be fixed, since it is working on my laptop.
>
> Regards,
> Ray L.
>
Group: DynoMotion Message: 3728 From: himykabibble Date: 2/5/2012
Subject: Re: VS2008 Question
Brad,

What's really infuriating is the error messages it gives are completely misleading. It kept telling me I didn't have .NET 3.5 installed! When I tried to install it, I'd get an error dialog from the installer that took up have the page, and contained just the two words: "Setup error". NO other information! And it was already installed and working fine!

I just today added to my app the ability to set axis parameters on-the-fly, and it updates the DSP, CoordMotion and Interpreter, all from a single data source. No more worries about different parts of the system using different parameters. If Tom can get to the bottom of the trajectory planner problem I'm having (it's not using the parameters I configure it with, and appears to end up with some crazy high acceleration for Z....), I will be in business! Everything else appears to be working quite nicely now.

BTW =- Found another naming error in dotNet - What should be ReadLineTimeout is actually "ReadLineTimout" - missing an 'e'.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@...> wrote:
>
> Everything works until the new .NET library is available in 4.29.. mu hu ha
> ha hah!
>
>
>
>
>
> There are lots of tightened bolts and extra goodies, so I do believe it will
> be work the effort to update.
>
>
>
> -Brad Murry
>
>
>
> From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> Behalf Of himykabibble
> Sent: Sunday, February 05, 2012 6:29 PM
> To: DynoMotion@yahoogroups.com
> Subject: [DynoMotion] Re: VS2008 Question
>
>
>
>
>
> OK, I've just learned something about the vagaries of .NET and VS2008.
> VS2008 does not fully understand .NET 4.0, and will sometimes get confused
> if you're running a project that uses it. This happened on the PC on my
> machine yesterday, and it happened on my laptop today. I spent hours trying
> to figure out what was wrong and how to fix it, with no joy. Then I stumbled
> across a simple fix - Under Project->Properties->Application, I set the
> target Framework to .NET 1.0, knowing full well it would break everything.
> And boy did it! I then set it BACK to .NET 3.5, and now life is good, and
> everything works as it should!
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> "himykabibble" <jagboy@> wrote:
> >
> > Brad,
> >
> > Thanks to Tom, I got my app moved over to VS2008, so I can now debug down
> into the DLLs (it appears VS2010 Express does not support this). It's all
> working fine on my laptop, but I also need it working on the PC on my
> machine. I copied over my entire KMotion428 tree, along with the project
> tree for my app. However, when I try to open BuildAllLibs.sln, I get an
> error message on KMotion_dotNet.csproj that reads:
> >
> > Unable to read the project file KMotion_dotNet.csproj
> >
> C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9
> ): The attribute "Returns" in element <Target> is unrecognized.
> >
> > I have had no success trying to understand what the problem is, much less
> resolve it. I suspect it has something to do with the fact that VS2008 does
> not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't
> know how to fix this. It clearly CAN be fixed, since it is working on my
> laptop.
> >
> > Regards,
> > Ray L.
> >
>
Group: DynoMotion Message: 3729 From: himykabibble Date: 2/5/2012
Subject: Re: VS2008 Question
Brad,

Just noticed something. When my app exits, I get the following dump, indicating there are memory leaks. Is it even possible for my app to generate these? Or is it coming from dotNet? If my app, any ideas how to find them?

Regards,
Ray L.

Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {112} normal block at 0x07A06128, 244 bytes long.
Data: < v Da v > 20 76 A0 07 44 61 A0 07 FC 76 A0 07 02 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {111} normal block at 0x07A07620, 244 bytes long.
Data: < <v > 00 00 00 00 3C 76 A0 07 00 00 00 00 01 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {101} normal block at 0x07A07540, 164 bytes long.
Data: < Tu > 00 00 00 00 54 75 A0 07 00 00 00 00 00 00 00 00
{89} The thread 'Win32 Thread' (0x1388) has exited with code 0 (0x0).
normal block at 0x07A027C8, 53 bytes long.
Data: < 5 $ $ > 80 AD 35 07 24 00 00 00 24 00 00 00 01 00 00 00
{78} normal block at 0x07A025D0, 248 bytes long.
Data: < 9 $@> 98 CD 39 04 CD CD CD CD 00 00 00 00 00 00 24 40
{68} normal block at 0x07A05DA0, 248 bytes long.
Data: < 9 >@> 98 CD 39 04 CD CD CD CD 00 00 00 00 00 00 3E 40
Object dump complete.
Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {492} normal block at 0x073CCF58, 37 bytes long.
Data: <<N x > 3C 4E A4 78 14 00 00 00 14 00 00 00 01 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {488} normal block at 0x073CCA60, 28 bytes long.
Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
{487} client block at 0x073CCA18, subtype c0, 12 bytes long.
faulted while dumping object at $073CCA18, 12 bytes long
c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(1270) : {486} normal block at 0x07A70068, 173584 bytes long.
Data: <D > 44 BB 03 04 CD CD CD CD 00 00 00 00 CD CD CD CD
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {485} normal block at 0x073CC9C0, 28 bytes long.
Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
{484} client block at 0x073CC978, subtype c0, 12 bytes long.
faulted while dumping object at $073CC978, 12 bytes long
c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(1002) : {483} normal block at 0x073CC5B0, 904 bytes long.
Data: <8 ] > 38 BB 03 04 CD CD CD CD A0 5D A0 07 D0 EB 08 04
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {480} normal block at 0x073CC548, 37 bytes long.
Data: <<N x > 3C 4E A4 78 14 00 00 00 14 00 00 00 01 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {473} normal block at 0x073CC4F0, 28 bytes long.
Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
{472} client block at 0x073CC4A8, subtype c0, 12 bytes long.
faulted while dumping object at $073CC4A8, 12 bytes long
c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(150) : {471} normal block at 0x073CC448, 32 bytes long.
Data: < < > D0 BA 03 04 A8 C4 3C 07 01 00 CD CD B9 15 02 04
Object dump complete.
The program '[0xE0C] CNCController.exe: Managed' has exited with code 0 (0x0).
The program '[0xE0C] CNCController.exe: Native' has exited with code 0 (0x0).


--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> What's really infuriating is the error messages it gives are completely misleading. It kept telling me I didn't have .NET 3.5 installed! When I tried to install it, I'd get an error dialog from the installer that took up have the page, and contained just the two words: "Setup error". NO other information! And it was already installed and working fine!
>
> I just today added to my app the ability to set axis parameters on-the-fly, and it updates the DSP, CoordMotion and Interpreter, all from a single data source. No more worries about different parts of the system using different parameters. If Tom can get to the bottom of the trajectory planner problem I'm having (it's not using the parameters I configure it with, and appears to end up with some crazy high acceleration for Z....), I will be in business! Everything else appears to be working quite nicely now.
>
> BTW =- Found another naming error in dotNet - What should be ReadLineTimeout is actually "ReadLineTimout" - missing an 'e'.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Everything works until the new .NET library is available in 4.29.. mu hu ha
> > ha hah!
> >
> >
> >
> >
> >
> > There are lots of tightened bolts and extra goodies, so I do believe it will
> > be work the effort to update.
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > Behalf Of himykabibble
> > Sent: Sunday, February 05, 2012 6:29 PM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] Re: VS2008 Question
> >
> >
> >
> >
> >
> > OK, I've just learned something about the vagaries of .NET and VS2008.
> > VS2008 does not fully understand .NET 4.0, and will sometimes get confused
> > if you're running a project that uses it. This happened on the PC on my
> > machine yesterday, and it happened on my laptop today. I spent hours trying
> > to figure out what was wrong and how to fix it, with no joy. Then I stumbled
> > across a simple fix - Under Project->Properties->Application, I set the
> > target Framework to .NET 1.0, knowing full well it would break everything.
> > And boy did it! I then set it BACK to .NET 3.5, and now life is good, and
> > everything works as it should!
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> > "himykabibble" <jagboy@> wrote:
> > >
> > > Brad,
> > >
> > > Thanks to Tom, I got my app moved over to VS2008, so I can now debug down
> > into the DLLs (it appears VS2010 Express does not support this). It's all
> > working fine on my laptop, but I also need it working on the PC on my
> > machine. I copied over my entire KMotion428 tree, along with the project
> > tree for my app. However, when I try to open BuildAllLibs.sln, I get an
> > error message on KMotion_dotNet.csproj that reads:
> > >
> > > Unable to read the project file KMotion_dotNet.csproj
> > >
> > C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9
> > ): The attribute "Returns" in element <Target> is unrecognized.
> > >
> > > I have had no success trying to understand what the problem is, much less
> > resolve it. I suspect it has something to do with the fact that VS2008 does
> > not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't
> > know how to fix this. It clearly CAN be fixed, since it is working on my
> > laptop.
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>
Group: DynoMotion Message: 3731 From: Brad Murry Date: 2/5/2012
Subject: Re: VS2008 Question

Hello Ray,

 

Keep in mind that we have to leave some pointers in place even after they leave scope so that state is maintained(things like an instance of CKMotionDLL needs to have the same variable data each time you access it).  This is a test criteria for the debugging tools you are using and is likely the origin of them.

 

 

To be safe, I will have another look at the ’leaks’ but I am pretty certain things are getting cleared out in the dispose methods that eventually do free the pointers as designed. 

 

 

-Brad Murry

 

From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On Behalf Of himykabibble
Sent: Sunday, February 05, 2012 8:16 PM
To: DynoMotion@yahoogroups.com
Subject: [DynoMotion] Re: VS2008 Question

 

 

Brad,

Just noticed something. When my app exits, I get the following dump, indicating there are memory leaks. Is it even possible for my app to generate these? Or is it coming from dotNet? If my app, any ideas how to find them?

Regards,
Ray L.

Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {112} normal block at 0x07A06128, 244 bytes long.
Data: < v Da v > 20 76 A0 07 44 61 A0 07 FC 76 A0 07 02 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {111} normal block at 0x07A07620, 244 bytes long.
Data: < <v > 00 00 00 00 3C 76 A0 07 00 00 00 00 01 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {101} normal block at 0x07A07540, 164 bytes long.
Data: < Tu > 00 00 00 00 54 75 A0 07 00 00 00 00 00 00 00 00
{89} The thread 'Win32 Thread' (0x1388) has exited with code 0 (0x0).
normal block at 0x07A027C8, 53 bytes long.
Data: < 5 $ $ > 80 AD 35 07 24 00 00 00 24 00 00 00 01 00 00 00
{78} normal block at 0x07A025D0, 248 bytes long.
Data: < 9 $@> 98 CD 39 04 CD CD CD CD 00 00 00 00 00 00 24 40
{68} normal block at 0x07A05DA0, 248 bytes long.
Data: < 9 >@> 98 CD 39 04 CD CD CD CD 00 00 00 00 00 00 3E 40
Object dump complete.
Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {492} normal block at 0x073CCF58, 37 bytes long.
Data: <<N x > 3C 4E A4 78 14 00 00 00 14 00 00 00 01 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {488} normal block at 0x073CCA60, 28 bytes long.
Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
{487} client block at 0x073CCA18, subtype c0, 12 bytes long.
faulted while dumping object at $073CCA18, 12 bytes long
c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(1270) : {486} normal block at 0x07A70068, 173584 bytes long.
Data: <D > 44 BB 03 04 CD CD CD CD 00 00 00 00 CD CD CD CD
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {485} normal block at 0x073CC9C0, 28 bytes long.
Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
{484} client block at 0x073CC978, subtype c0, 12 bytes long.
faulted while dumping object at $073CC978, 12 bytes long
c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(1002) : {483} normal block at 0x073CC5B0, 904 bytes long.
Data: <8 ] > 38 BB 03 04 CD CD CD CD A0 5D A0 07 D0 EB 08 04
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {480} normal block at 0x073CC548, 37 bytes long.
Data: <<N x > 3C 4E A4 78 14 00 00 00 14 00 00 00 01 00 00 00
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {473} normal block at 0x073CC4F0, 28 bytes long.
Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
{472} client block at 0x073CC4A8, subtype c0, 12 bytes long.
faulted while dumping object at $073CC4A8, 12 bytes long
c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(150) : {471} normal block at 0x073CC448, 32 bytes long.
Data: < < > D0 BA 03 04 A8 C4 3C 07 01 00 CD CD B9 15 02 04
Object dump complete.
The program '[0xE0C] CNCController.exe: Managed' has exited with code 0 (0x0).
The program '[0xE0C] CNCController.exe: Native' has exited with code 0 (0x0).

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Brad,
>
> What's really infuriating is the error messages it gives are completely misleading. It kept telling me I didn't have .NET 3.5 installed! When I tried to install it, I'd get an error dialog from the installer that took up have the page, and contained just the two words: "Setup error". NO other information! And it was already installed and working fine!
>
> I just today added to my app the ability to set axis parameters on-the-fly, and it updates the DSP, CoordMotion and Interpreter, all from a single data source. No more worries about different parts of the system using different parameters. If Tom can get to the bottom of the trajectory planner problem I'm having (it's not using the parameters I configure it with, and appears to end up with some crazy high acceleration for Z....), I will be in business! Everything else appears to be working quite nicely now.
>
> BTW =- Found another naming error in dotNet - What should be ReadLineTimeout is actually "ReadLineTimout" - missing an 'e'.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Everything works until the new .NET library is available in 4.29.. mu hu ha
> > ha hah!
> >
> >
> >
> >
> >
> > There are lots of tightened bolts and extra goodies, so I do believe it will
> > be work the effort to update.
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > Behalf Of himykabibble
> > Sent: Sunday, February 05, 2012 6:29 PM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] Re: VS2008 Question
> >
> >
> >
> >
> >
> > OK, I've just learned something about the vagaries of .NET and VS2008.
> > VS2008 does not fully understand .NET 4.0, and will sometimes get confused
> > if you're running a project that uses it. This happened on the PC on my
> > machine yesterday, and it happened on my laptop today. I spent hours trying
> > to figure out what was wrong and how to fix it, with no joy. Then I stumbled
> > across a simple fix - Under Project->Properties->Application, I set the
> > target Framework to .NET 1.0, knowing full well it would break everything.
> > And boy did it! I then set it BACK to .NET 3.5, and now life is good, and
> > everything works as it should!
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> > "himykabibble" <jagboy@> wrote:
> > >
> > > Brad,
> > >
> > > Thanks to Tom, I got my app moved over to VS2008, so I can now debug down
> > into the DLLs (it appears VS2010 Express does not support this). It's all
> > working fine on my laptop, but I also need it working on the PC on my
> > machine. I copied over my entire KMotion428 tree, along with the project
> > tree for my app. However, when I try to open BuildAllLibs.sln, I get an
> > error message on KMotion_dotNet.csproj that reads:
> > >
> > > Unable to read the project file KMotion_dotNet.csproj
> > >
> > C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9
> > ): The attribute "Returns" in element <Target> is unrecognized.
> > >
> > > I have had no success trying to understand what the problem is, much less
> > resolve it. I suspect it has something to do with the fact that VS2008 does
> > not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't
> > know how to fix this. It clearly CAN be fixed, since it is working on my
> > laptop.
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>
Group: DynoMotion Message: 3733 From: Tom Kerekes Date: 2/5/2012
Subject: Re: VS2008 Question
Ray,
 
The problem with the wierd trajectory plots is being caused because the Trajectory Planner settings are being set in counts rather than inches.  So the velocities and accelerations are being set ~5000X too high.  Below is the corrected code.  CoordMotion and the Trajectory Planner work in units of inches.  Only the parameters in KFLOP are set in counts and used for independent motions.
 
Funny in an earlier email you set a breakpoint and told me the "AccelToUse variable was "50800 which is correct for that axis" and I didn't catch it either because I didn't question your statement. 
 
Also as a side note the duplication of settings caused by two instances of CoordMotion in the .NET interface will be eliminated in the next release that Brad did for us.
 
Regards
TK
 
 
private void InitAxisParameters()
{
// Update DSP axis parameters
UploadAxisParameters();
Thread.Sleep(500);
// Update CoordMotion and Interpreter axis parameters
KMController.WriteLine(
"DisableAxis0");
KMController.CoordMotion.MotionParams.CountsPerInchX =
MachineConfigBall.X_STEPS_PER_INCH;
KMController.CoordMotion.MotionParams.MaxVelX =
MachineConfigBall.X_MAX_VEL_IPM / 60;
KMController.CoordMotion.MotionParams.MaxAccelX =
MachineConfigBall.X_ACCEL_IN_PER_SEC2;
KMController.Interpreter.CountsPerInchX =
MachineConfigBall.X_STEPS_PER_INCH;
KMController.Interpreter.MaxVelX =
MachineConfigBall.X_MAX_VEL_IPM / 60;
KMController.Interpreter.MaxAccelX =
MachineConfigBall.X_ACCEL_IN_PER_SEC2;
KMController.WriteLine(
"EnableAxis0");
KMController.WriteLine(
"DisableAxis1");
KMController.CoordMotion.MotionParams.CountsPerInchY =
MachineConfigBall.Y_STEPS_PER_INCH;
KMController.CoordMotion.MotionParams.MaxVelY =
MachineConfigBall.Y_MAX_VEL_IPM / 60;
KMController.CoordMotion.MotionParams.MaxAccelY =
MachineConfigBall.Y_ACCEL_IN_PER_SEC2;
KMController.Interpreter.CountsPerInchY =
MachineConfigBall.Y_STEPS_PER_INCH;
KMController.Interpreter.MaxVelY =
MachineConfigBall.Y_MAX_VEL_IPM / 60;
KMController.Interpreter.MaxAccelY =
MachineConfigBall.Y_ACCEL_IN_PER_SEC2;
KMController.WriteLine(
"EnableAxis1");
KMController.WriteLine(
"DisableAxis2");
KMController.CoordMotion.MotionParams.CountsPerInchZ =
MachineConfigBall.Z_STEPS_PER_INCH;
KMController.CoordMotion.MotionParams.MaxVelZ =
MachineConfigBall.Z_MAX_VEL_IPM / 60;
KMController.CoordMotion.MotionParams.MaxAccelZ =
MachineConfigBall.Z_ACCEL_IN_PER_SEC2;
KMController.Interpreter.CountsPerInchZ =
MachineConfigBall.Z_STEPS_PER_INCH;
KMController.Interpreter.MaxVelZ =
MachineConfigBall.Z_MAX_VEL_IPM / 60;
KMController.Interpreter.MaxAccelZ =
MachineConfigBall.Z_ACCEL_IN_PER_SEC2;
KMController.WriteLine(
"EnableAxis2");
KMController.WriteLine(
"DisableAxis3");
KMController.CoordMotion.MotionParams.CountsPerInchA =
MachineConfigBall.A_STEPS_PER_INCH;
KMController.CoordMotion.MotionParams.MaxVelA =
MachineConfigBall.A_MAX_VEL_IPM / 60;
KMController.CoordMotion.MotionParams.MaxAccelA =
MachineConfigBall.A_ACCEL_IN_PER_SEC2;
KMController.Interpreter.CountsPerInchA =
MachineConfigBall.A_STEPS_PER_INCH;
KMController.Interpreter.MaxVelA =
MachineConfigBall.A_MAX_VEL_COUNTS;
KMController.Interpreter.MaxAccelA =
MachineConfigBall.A_ACCEL_IN_PER_SEC2;
KMController.WriteLine(
"EnableAxis3");

Group: DynoMotion Message: 3735 From: himykabibble Date: 2/5/2012
Subject: Re: VS2008 Question
Tom,

I knew it would turn out to be something simple!

This is exciting! With that fixed, I'm quite confident things will go very well in the shop tomorrow!

Thank you VERY much for sorting that out! I never would've found that! I've sorted out a couple of other minor bugs today, so I'm feeling pretty good about the condition of my app now.

Regards,
Ray L.


--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Ray,
>  
> The problem with the wierd trajectory plots is being caused because the Trajectory Planner settings are being set in counts rather than inches.  So the velocities and accelerations are being set ~5000X too high.  Below is the corrected code.  CoordMotion and the Trajectory Planner work in units of inches.  Only the parameters in KFLOP are set in counts and used for independent motions.
>  
> Funny in an earlier email you set a breakpoint and told me the "AccelToUse variable was "50800 which is correct for that axis" and I didn't catch it either because I didn't question your statement. 
>  
> Also as a side note the duplication of settings caused by two instances of CoordMotion in the .NET interface will be eliminated in the next release that Brad did for us.
>  
> Regards
> TK
>  
>  {privatevoidInitAxisParameters()// Update DSP axis parametersUploadAxisParameters();Thread.Sleep(500);// Update CoordMotion and Interpreter axis parametersKMController.WriteLine(
> KMController.CoordMotion.MotionParams.CountsPerInchX =
> KMController.CoordMotion.MotionParams.MaxVelX =
> KMController.CoordMotion.MotionParams.MaxAccelX =
> KMController.Interpreter.CountsPerInchX =
> KMController.Interpreter.MaxVelX =
> KMController.Interpreter.MaxAccelX =
> KMController.WriteLine(
> KMController.WriteLine(
> KMController.CoordMotion.MotionParams.CountsPerInchY =
> KMController.CoordMotion.MotionParams.MaxVelY =
> KMController.CoordMotion.MotionParams.MaxAccelY =
> KMController.Interpreter.CountsPerInchY =
> KMController.Interpreter.MaxVelY =
> KMController.Interpreter.MaxAccelY =
> KMController.WriteLine(
> KMController.WriteLine(
> KMController.CoordMotion.MotionParams.CountsPerInchZ =
> KMController.CoordMotion.MotionParams.MaxVelZ =
> KMController.CoordMotion.MotionParams.MaxAccelZ =
> KMController.Interpreter.CountsPerInchZ =
> KMController.Interpreter.MaxVelZ =
> KMController.Interpreter.MaxAccelZ =
> KMController.WriteLine(
> KMController.WriteLine(
> KMController.CoordMotion.MotionParams.CountsPerInchA =
> KMController.CoordMotion.MotionParams.MaxVelA =
> KMController.CoordMotion.MotionParams.MaxAccelA =
> KMController.Interpreter.CountsPerInchA =
> KMController.Interpreter.MaxVelA =
> KMController.Interpreter.MaxAccelA =
> KMController.WriteLine("DisableAxis0");MachineConfigBall.X_STEPS_PER_INCH;MachineConfigBall.X_MAX_VEL_IPM / 60;MachineConfigBall.X_ACCEL_IN_PER_SEC2;MachineConfigBall.X_STEPS_PER_INCH;MachineConfigBall.X_MAX_VEL_IPM / 60;MachineConfigBall.X_ACCEL_IN_PER_SEC2;"EnableAxis0");"DisableAxis1");MachineConfigBall.Y_STEPS_PER_INCH;MachineConfigBall.Y_MAX_VEL_IPM / 60;MachineConfigBall.Y_ACCEL_IN_PER_SEC2;MachineConfigBall.Y_STEPS_PER_INCH;MachineConfigBall.Y_MAX_VEL_IPM / 60;MachineConfigBall.Y_ACCEL_IN_PER_SEC2;"EnableAxis1");"DisableAxis2");MachineConfigBall.Z_STEPS_PER_INCH;MachineConfigBall.Z_MAX_VEL_IPM / 60;MachineConfigBall.Z_ACCEL_IN_PER_SEC2;MachineConfigBall.Z_STEPS_PER_INCH;MachineConfigBall.Z_MAX_VEL_IPM / 60;MachineConfigBall.Z_ACCEL_IN_PER_SEC2;"EnableAxis2");"DisableAxis3");MachineConfigBall.A_STEPS_PER_INCH;MachineConfigBall.A_MAX_VEL_IPM /
> 60;MachineConfigBall.A_ACCEL_IN_PER_SEC2;MachineConfigBall.A_STEPS_PER_INCH;MachineConfigBall.A_MAX_VEL_COUNTS;MachineConfigBall.A_ACCEL_IN_PER_SEC2;"EnableAxis3");
>
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, February 5, 2012 7:15 PM
> Subject: [DynoMotion] Re: VS2008 Question
>
>
>  
> Brad,
>
> Just noticed something. When my app exits, I get the following dump, indicating there are memory leaks. Is it even possible for my app to generate these? Or is it coming from dotNet? If my app, any ideas how to find them?
>
> Regards,
> Ray L.
>
> Detected memory leaks!
> Dumping objects ->
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {112} normal block at 0x07A06128, 244 bytes long.
> Data: < v Da v > 20 76 A0 07 44 61 A0 07 FC 76 A0 07 02 00 00 00
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {111} normal block at 0x07A07620, 244 bytes long.
> Data: < <v > 00 00 00 00 3C 76 A0 07 00 00 00 00 01 00 00 00
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\plex.cpp(29) : {101} normal block at 0x07A07540, 164 bytes long.
> Data: < Tu > 00 00 00 00 54 75 A0 07 00 00 00 00 00 00 00 00
> {89} The thread 'Win32 Thread' (0x1388) has exited with code 0 (0x0).
> normal block at 0x07A027C8, 53 bytes long.
> Data: < 5 $ $ > 80 AD 35 07 24 00 00 00 24 00 00 00 01 00 00 00
> {78} normal block at 0x07A025D0, 248 bytes long.
> Data: < 9 $@> 98 CD 39 04 CD CD CD CD 00 00 00 00 00 00 24 40
> {68} normal block at 0x07A05DA0, 248 bytes long.
> Data: < 9 >@> 98 CD 39 04 CD CD CD CD 00 00 00 00 00 00 3E 40
> Object dump complete.
> Detected memory leaks!
> Dumping objects ->
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {492} normal block at 0x073CCF58, 37 bytes long.
> Data: <<N x > 3C 4E A4 78 14 00 00 00 14 00 00 00 01 00 00 00
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {488} normal block at 0x073CCA60, 28 bytes long.
> Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
> {487} client block at 0x073CCA18, subtype c0, 12 bytes long.
> faulted while dumping object at $073CCA18, 12 bytes long
> c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(1270) : {486} normal block at 0x07A70068, 173584 bytes long.
> Data: <D > 44 BB 03 04 CD CD CD CD 00 00 00 00 CD CD CD CD
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {485} normal block at 0x073CC9C0, 28 bytes long.
> Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
> {484} client block at 0x073CC978, subtype c0, 12 bytes long.
> faulted while dumping object at $073CC978, 12 bytes long
> c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(1002) : {483} normal block at 0x073CC5B0, 904 bytes long.
> Data: <8 ] > 38 BB 03 04 CD CD CD CD A0 5D A0 07 D0 EB 08 04
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {480} normal block at 0x073CC548, 37 bytes long.
> Data: <<N x > 3C 4E A4 78 14 00 00 00 14 00 00 00 01 00 00 00
> f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(141) : {473} normal block at 0x073CC4F0, 28 bytes long.
> Data: <<N x > 3C 4E A4 78 0B 00 00 00 0B 00 00 00 01 00 00 00
> {472} client block at 0x073CC4A8, subtype c0, 12 bytes long.
> faulted while dumping object at $073CC4A8, 12 bytes long
> c:\kmotion428\kmotion_dotnet_interop\kmotion_dotnet_interop.cpp(150) : {471} normal block at 0x073CC448, 32 bytes long.
> Data: < < > D0 BA 03 04 A8 C4 3C 07 01 00 CD CD B9 15 02 04
> Object dump complete.
> The program '[0xE0C] CNCController.exe: Managed' has exited with code 0 (0x0).
> The program '[0xE0C] CNCController.exe: Native' has exited with code 0 (0x0).
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@> wrote:
> >
> > Brad,
> >
> > What's really infuriating is the error messages it gives are completely misleading. It kept telling me I didn't have .NET 3.5 installed! When I tried to install it, I'd get an error dialog from the installer that took up have the page, and contained just the two words: "Setup error". NO other information! And it was already installed and working fine!
> >
> > I just today added to my app the ability to set axis parameters on-the-fly, and it updates the DSP, CoordMotion and Interpreter, all from a single data source. No more worries about different parts of the system using different parameters. If Tom can get to the bottom of the trajectory planner problem I'm having (it's not using the parameters I configure it with, and appears to end up with some crazy high acceleration for Z....), I will be in business! Everything else appears to be working quite nicely now.
> >
> > BTW =- Found another naming error in dotNet - What should be ReadLineTimeout is actually "ReadLineTimout" - missing an 'e'.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > >
> > > Everything works until the new .NET library is available in 4.29.. mu hu ha
> > > ha hah!
> > >
> > >
> > >
> > >
> > >
> > > There are lots of tightened bolts and extra goodies, so I do believe it will
> > > be work the effort to update.
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > > Behalf Of himykabibble
> > > Sent: Sunday, February 05, 2012 6:29 PM
> > > To: DynoMotion@yahoogroups.com
> > > Subject: [DynoMotion] Re: VS2008 Question
> > >
> > >
> > >
> > >
> > >
> > > OK, I've just learned something about the vagaries of .NET and VS2008.
> > > VS2008 does not fully understand .NET 4.0, and will sometimes get confused
> > > if you're running a project that uses it. This happened on the PC on my
> > > machine yesterday, and it happened on my laptop today. I spent hours trying
> > > to figure out what was wrong and how to fix it, with no joy. Then I stumbled
> > > across a simple fix - Under Project->Properties->Application, I set the
> > > target Framework to .NET 1.0, knowing full well it would break everything.
> > > And boy did it! I then set it BACK to .NET 3.5, and now life is good, and
> > > everything works as it should!
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com <mailto:DynoMotion%40yahoogroups.com> ,
> > > "himykabibble" <jagboy@> wrote:
> > > >
> > > > Brad,
> > > >
> > > > Thanks to Tom, I got my app moved over to VS2008, so I can now debug down
> > > into the DLLs (it appears VS2010 Express does not support this). It's all
> > > working fine on my laptop, but I also need it working on the PC on my
> > > machine. I copied over my entire KMotion428 tree, along with the project
> > > tree for my app. However, when I try to open BuildAllLibs.sln, I get an
> > > error message on KMotion_dotNet.csproj that reads:
> > > >
> > > > Unable to read the project file KMotion_dotNet.csproj
> > > >
> > > C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets(132,9
> > > ): The attribute "Returns" in element <Target> is unrecognized.
> > > >
> > > > I have had no success trying to understand what the problem is, much less
> > > resolve it. I suspect it has something to do with the fact that VS2008 does
> > > not seem to really "grok" .NET4.0, but rather only up to 3.5. But I don't
> > > know how to fix this. It clearly CAN be fixed, since it is working on my
> > > laptop.
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > >
> >
>